Repository navigation
feat(installer): support prerelease installations - #3364
Conversation
|
🌿 Preview your docs: https://nvidia-preview-pr-3364.docs.buildwithfern.com/openshell |
This comment was marked as outdated.
This comment was marked as outdated.
elezar
left a comment
There was a problem hiding this comment.
Let's get this in and iterate.
45c2d17 to
3e553f8
Compare
|
One remaining blocker is that prerelease aliases can expose an unqualified candidate:
Could we make qualification explicit with this ordering?
I'd also have the rolling Helm chart pin the qualified candidate's exact image version. That prevents a later image-channel update from silently changing an already-published chart. This preserves the current Actions-artifact approach while ensuring every rolling prerelease entry point means "latest qualified candidate." |
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
4ba363d to
79f7fd4
Compare
|
Thanks — addressed by simplifying the prerelease model instead of adding a rolling promotion stage.
With no rolling prerelease images or charts remaining, there is no separate promotion step or mutable chart-to-image mapping to qualify. |
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Piotr Mlocek <pmlocek@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
Summary
Add first-class prerelease installation support for local and Kubernetes users, and announce the upcoming OpenShell 0.1.0 release in the README and Fern documentation. Prerelease packages are retained as authenticated GitHub Actions artifacts rather than published as GitHub Releases; Kubernetes installs reuse the exact image and Helm chart versions the Release Tag workflow already publishes.
Related Issue
Related to #2860
Changes
OPENSHELL_VERSION=preto the latest current-platform artifact from a completed, successful Release Tag workflow runheadBranchassumptions and reject expired artifacts during discovery and exact-version installation<version>-pre.NHelm chart versions for Kubernetes installsTesting
mise run pre-commitmise run test:install-shmise run docs(0 errors; 3 existing warnings)uv run pytest python/release_tooling_test.py python/openshell/release_formula_test.py -qmise run helm:docs:checkmise x github:rhysd/actionlint@v1.7.12 -- actionlint -shellcheck= .github/workflows/release-tag.ymlmise run test(all relevant suites passed; the unrelatedtest:e2e-parityharness failed because its synthetic baseline/candidate launchers did not emit retained manifests)Checklist